Don't wirelessly link an ItemStack's component to a live player#909
Merged
imreallybadatnames merged 1 commit intoJun 15, 2026
Conversation
imreallybadatnames
approved these changes
Jun 15, 2026
imreallybadatnames
left a comment
imreallybadatnames
left a comment
Collaborator
There was a problem hiding this comment.
satisfactory
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Per neoforge docs (but it's a minecraft's own class, they just documented some about it):
Stops the item stack from having an effect updated by the player's effect ticking down. Or whatever might be going on in the depths of minecraft codebase.
Also behaved really oddly (crash potentially?) when you tried to store it in some mods' special item containers